System and method for static and dynamic load analyses of communication network

ABSTRACT

The proposed system defines a predictive real-time Service Level Agreements (SLAs) monitoring system by (a) a detailed analysis of traffic flows with reduced monitor-data flow across network; and (b) a suitable combination of offline and real-time processing of historical and current traffic data. In order to be able to undertake a detailed analysis without significantly impacting the network throughput, the system analyzes the historical traffic patterns of a typical Provider&#39;s network to determine a set of critical SLAs. An in-depth analysis of traffic is performed by creating a unique network parent probe for every critical SLA and the parent probe spawns an optimal number of intelligent master and slave probes based on a regionalization procedure. The online overload monitoring system analyzes the gathered data from the master and slave probes to (a) forecast future violations of the SLA under consideration based on multiple forecast models and (b) generate operator SLA violation alarms.

FIELD OF INVENTION

[0001] This present invention relates to real-time monitoring of SLAs in general and more particularly monitoring a subset of SLAs. Still more particularly, the present invention relates to a system and method for prediction of operator SLA violation based on monitor-data.

BACKGROUND OF INVENTION

[0002] A Service Level Agreement (SLA) is a contract between two parties, the service provider and a subscriber, or between two service providers, that specifies, in terms of metrics, the type and level of service that can be obtained from the service provider. The metrics are measurable QoS parameters with agreed upon threshold values. Failure to meet these thresholds result in penalties, which are degrees of compensations mutually, agreed upon by the service provider and customer. Network and service performance need to be monitored for their degradation in order to avoid SLA violations, which might cause the provider to pay penalties. Therefore, real-time traffic flows across network segments need to be closely monitored for performance degradations.

[0003] A real-time monitoring system generally monitors network traffic for violation of threshold values agreed upon in SLAs and appropriately sends alarms to the operator in the event of any violations. Threshold violations of agreed upon terms is determined by monitoring all the SLAs and the monitor-data for traffic analysis is generally collected from the network elements by launching agents in all the network elements. Reporting tools have been developed for offline analysis of historic traffic data to generate trend reports for future traffic behavior. Real-time monitoring of SLAs have an impact on the network traffic since network agents that are installed in the various network elements generate continuous monitor-data related to the SLAs to help determine SLA violations. Real-time monitoring of networks are generally performed using two types of methods, namely, passive methods (non-intrusive monitoring) and active methods (intrusive monitoring). Passive methods generally retrieve the information from the packets that are received by a network element by reading the packet-header information and hence non-intrusive characteristics are used by passive methods for monitoring the network. Active methods retrieve information related to performance parameters by injecting additional probe packets across the network and hence intrusive characteristics are used by active methods for monitoring the network. The additional probe packets are inserted in between normal data packets. Real-time monitoring of SLAs is also performed by implementing a policy-based network architecture, which comprises of translating the SLAs into policies. The policies are then specified and entered into to a Policy Server. These policies can either be dynamic or static. Dynamic policies specify how to react when a particular criterion is met. Static policies basically check for the validity of defined criteria. Policy servers read the defined policies from a repository, determine the targets, and forward the policy information to appropriate policy agents/clients that reside in the network element. Then, policy clients translate the policy information received from the policy server and convert it to element specific configurations. The policy clients continuously monitor for these dynamic and static policies and respond to the policy server or take some action based on defined criteria.

[0004] Regardless of the usefulness of network monitor-data to operators for the purposes of network management, monitoring will quickly be discontinued if the network overhead due to monitor-data increases to such a point that the flow of data through the network is adversely affected. The monitoring of data should be in such a way that the measurement tools can remain in operation at all times, especially during high workload and system stress situations.

[0005] The present invention reduces the monitor-data flow across the network by monitoring only a subset of the SLAs and by optimally distributing the “intelligent” network probes across the network. The subset of SLAs to be monitored is identified based on an optimal analysis of the network load and past violation patterns. The optimal distribution of network probes is based on the “load similarity” of the nodes of the network and due to this aspect of the network nodes, the probes in the select network nodes are capable of computing the network load due to the subset of SLAs by predicting the load at rest of the nodes based on the notion of similarity. This approach leads to the reduction in monitor-data flow across the network.

[0006] the nodes based on the notion of similarity. This approach leads to the reduction in monitor-data flow across the network.

[0007] Revenue enhancement is one of the key requirements of any network provider. The key factors for sustained revenue generation are management of network capacity, penalty reduction by providing service assurance as contractually agreed in an SLA, and retaining the subscribers by reducing churn rate.

[0008] The objective of the network capacity management is to be able to successfully load the network to its capacity. By reducing the monitor-data flow within a network, more network bandwidth is available for carrying payload and hence contributing to increased revenue to network provider. An additional way for the provider to enhance revenue is to allow for over-subscription. Under such conditions, there is a possibility of network overload leading to operator SLA violations. Hence, there is a need to establish a balance between penalty reduction and over-subscription. The present invention aims at generating operator violation alarm at a future time point based on cross-correlation of past and present usage pattern data. More accurate the operator violation predictions, higher are the chances for the operator to increase the revenue based on over-subscription.

[0009] U.S. Pat. No. 6,147,975 to Bowman-Amuah for “System, method and article of manufacture of a proactive threshold manager in a hybrid communication system architecture” (issued Nov. 14, 2000 and assigned to AC Properties B.V. (NL)) describes a proactive threshold manager that forewarns service providers of an impending breach of contract. The threshold manager sends an alarm to the service provider when the current level of service misses a service level agreement to maintain a certain level of service.

[0010] The above said invention makes use of real-time monitor-data related to all service level agreements to check the current level of service. This adds to the network congestion during the times of network overload. As compared to the above-mentioned patent, the present invention aims at reducing the monitor-data flow by monitoring a select set of SLAs and by a regionalization procedure to cluster the network nodes based on similar load behavior. In addition, the present invention generates alarms by combining the prediction of the current usage pattern based on a best possible, from a suite of forecasting models, model with the prediction of the usage pattern in the past based on a best possible, from a suite of forecasting models, model. Furthermore, the present invention makes the operator SLA violation prediction more realistic, and hence reduces the generation of false alarms, by analyzing the forecasted usage pattern trend and focusing on only those CSLAs where the load due to each such CSLA being below the contractually agreed upon bandwidth for that CSLA.

[0011] U.S. Pat. No. 6,272,110 to Tunnicliffe , et al. for “Method and apparatus for managing at least part of a communications network” (issued Aug. 7, 2001 and assigned to Nortel Networks Limited (Montreal, Calif.)) comprises of managing a communications (customer's) network by predicting sequential future values of a time-series of data (representative of traffic levels in the network) to determine whether they exceed bandwidth levels as defined in the SLA. In contrast to the above-mentioned patent, the present invention analyzes the traffic data at network-level as opposed to at customer-specific sub-network-level. Further, the present invention analyzes the load on the network from the network provider's perspective to reduce penalty situations.

[0012] Forecasting Techniques based on Time Series models have been applied to network resources in order to predict network traffic for the purposes of network management. “The Network Weather Service: A Distributed Resource Performance Forecasting Service for Metacomputing,” by Rich Wolski, Neil Spring, and Jim Hayes, describes the Network Weather Service, which is a distributed, generalized system for producing short-term performance forecasts based on historical performance measurement. A suite of forecasting models is applied over the entire time-series and the forecasting technique that has been most accurate over the recent set of measurements is dynamically chosen as the representative model.

[0013] “Design-Assisted, Real-time, Measurement-Based Network Controls for Management of Service Level Agreements,” by E. Bouillet, D. Mitra and K. G. Ramakrishnan, describes an SLA monitoring scheme that optimizes net revenue based on the flows related to a set of SLAs. This approach proposes two distinct phases: Offline phase that includes SLA crafting and online phase that includes real-time SLA management. Revenue gets generated by the admission of flows into the network and penalty is incurred when the service provider is not SLA compliant.

[0014] To summarize, the objectives of the present invention are the following:

[0015] An integrated Overload Monitoring System (OMS), for offline Critical Service Level Agreement (CSLA) Identification based on bandwidth (BW) and Near-Optimal Traffic Analysis for Forecasting BW-related CSLA Operator Violations at a future time point, comprising of:

[0016] a) offline procedures for critical SLA identification, regionalization of network nodes, historical data based forecast model selection, overall load due to critical SLAs and offline operator SLA violation prediction at a future time point;

[0017] b) universal network probes that perform a near-optimal analysis of the network traffic for critical SLAs; and

[0018] c) online procedures for network traffic analysis by the network probes based on two distinct configurable clocks, online operator SLA violation prediction at a future time point and consistency based alarm generation.

SUMMARY OF INVENTION

[0019] The primary objective of the invention is the creation of a subsystem for the offline identification and real-time monitoring of a select set of SLAs termed as critical SLAs. Critical SLAs are a subset of SLAs wherein a slight variation in the usage pattern by the network users bound by these SLAs would cause a network overload. The pre-installed network probes perform a near-optimal analysis of the network traffic for only the critical SLAs, thereby minimizing the monitor-data flow across the network. In addition, the probes perform forecasting of the network traffic due to the critical SLAs to predict Operator SLA violations.

[0020] The objective of the present invention is achieved by the interaction between the offline and online components of the Overload Monitoring System (OMS). The OMS-Offline comprises of a Critical SLA Identification Procedure that relates to the analysis of network traffic in terms of the network load (bandwidth) due to the critical SLAs.

[0021] When there is insufficient network data available from the external databases, a passive agent is installed in network elements of the network to collect the necessary traffic data and the OMS Offline Component pulls this data from the network elements during times of low network usage thereby reducing the data flow in the network.

[0022] The Critical SLA Identification Procedure of the OMS-Offline comprises of a procedure to identify four types of critical SLAs, namely, O-CSLAs, using an automatic SLA selection technique based on an optimization procedure, V-CSLAs, based on past violation history of the SLAs, M-CSLAs, based on a manual selection of SLAs by operators, and N-CSLAs, based on an agreed upon bandwidth, as per the SLA of new subscribers.

[0023] The OMS-Offline further comprises of a Hard Upper Bound (HUB) Procedure to compute the overall network load due to the identified critical SLAs at periodic time intervals. The load due to CSLAs is marginalized from the overall network load, by taking into account the UUBs of X-SLAs.

[0024] According to a preferred development of the invention, the OMS-Offline comprises of a Forecast Procedure to predict the load due to the critical SLAs using horizontal and vertical model selection techniques on the historical data. The Forecast Procedure further comprises of an Analysis Interval (AI) Identification Procedure that identifies appropriate forecast models (FM) for each of the AIs.

[0025] The OMS-Offline further comprises of a Node Regionalization Procedure, based on a hierarchical clustering procedure. This procedure clusters nodes related to each of CSLAs having similar average (mean) load characteristics. Clusters are formed for the nodes in the service providers network based on the physical contiguity of the network elements and are further grouped into Similar Load Sub-Clusters (SLSCs) based on similar mean characteristics.

[0026] The OMS-Online of the present invention involves the creation of a unique parent probe for every critical SLA. The pre-installed network probes are referred to as Universal Network Probes (UNPs) since they behave as either master or Slave network probes depending on the parameter that is communicated to them. A master network probe is identified, for each SLSC, based on the centroid of the SLSC and the rest of the nodes in the SLSC are identified as locations for Slave network probes.

[0027] According to an advantageous preferred development of the invention, two distinct configurable clocks, namely, the master clock and the Slave clock, are used in the analysis of the network traffic. The master clock frequency is much higher than the Slave clock frequency to facilitate reduced monitor-data flow across the network. The Slave probe filters and aggregates the load at the Slave clock rate and communicates the Slave node load to the master probe. The master probe in turn filters and aggregates the traffic data at the master clock rate and computes the SLSC load based on the load obtained from the master node and the Slave nodes.

[0028] The OMS-Online of the present invention further consists of a procedure wherein the parent probe forecasts the load due to the corresponding SLA at the master clock frequency, wherein, the forecast is for a set of future time points that are Time Before OverLoad (TBOL) units away from the time of forecast. The parent probe further communicates the forecasted load to the Alarm Monitoring Component (AMC).

[0029] According to an advantageous further development of the invention, the parent probe forecasts the traffic data initially using the forecasting model identified during the offline procedure and receives the updated forecast models at pre-defined regular intervals. The parent probes of the above invention are also capable of identifying the underlying trend around TBOL of the forecasted load pattern and communicate the trend behavior to the AMC.

[0030] The OMS-Online of the present invention further comprises of a procedure wherein the AMC, based on the forecasted load and trend information received from the parent probes, computes the overall network load due to the critical SLAs. The AMC further determines the overload condition, to check whether the forecasted load is an indication of the load exceeding network capacity, by comparing the overall network load due to the critical SLAs with the HUB determined during offline analysis.

[0031] According to an advantageous further development, the AMC of the above invention consists of a procedure for alarm prediction that sets an Alarm Set Point (ASP) for a critical SLA if there is a predicted network overload at a given TBOL time point based on the horizontal forecast models corresponding to the involved AIs. Further, the AMC consists of an alarm confirmation procedure that confirms the ASP and sets an Operator Violation Alarm (OVA) flag if there is a consistent network overload at successive time intervals based on the combined offline and online predictions.

[0032] The AMC of the present invention further comprises of an alarm generation and escalation procedure that generates an alarm if the OVA flag is set to all the pre-specified candidate operators and further escalates the alarm in case of the non-receipt of an acknowledgement for the generated OVA.

[0033] The passive agents installed in network elements of the network collect the necessary traffic data related to non-critical SLAs and the OMS Offline Component pulls this data from the network elements during times of low network usage thereby reducing the data flow in the network.

BRIEF DESCRIPTION OF THE DRAWINGS

[0034] FIG. A depicts the interaction between the offline and online components of the OMS.

[0035] FIG. B depicts the offline functionality of the components of the OMS.

[0036] FIG. B1 depicts the Critical SLA (CSLA) Identification Component.

[0037] FIG. B2 depicts the SLA Load Analysis Procedure and determination of SATWs.

[0038] FIG. B3 depicts the graphical representation of SATWs.

[0039] FIG. B4 depicts the steps in the Identification of O-CSLAs.

[0040] FIG. B5 depicts the steps in the Node Regionalization Procedure for an SLA

[0041] FIG. B6 depicts the Hierarchical Clustering Procedure.

[0042] FIG. B7 depicts the graphical representation of the Load due to the SLA and the Identification of Forecast Models.

[0043] FIG. B8 depicts the steps in the Model Selection Component.

[0044] FIG. B9 depicts the steps involved in the Merging of Analysis Intervals.

[0045] FIG. B10 depicts the graphical representation of the Merging of Analysis Intervals.

[0046] FIG. B11 depicts the steps in the DTP-wise HUB Computation.

[0047] FIG. B12 depicts the steps involved in offline prediction.

[0048] FIG. C depicts the online functionality of the components of the OMS.

[0049] FIG. C1 depicts the Probe Activation Component.

[0050] FIG. C2 depicts the Master Probe Component for the SLSC.

[0051] FIG. C3 depicts the Master Probe Component for the VLSC.

[0052] FIG. C4 depicts the Slave Probe Component.

[0053] FIG. C5 depicts the steps in the Parent Probe Forecast Component for the pth SLA.

[0054] FIG. C6 depicts the execution flow of the Alarm Manager Component.

[0055] FIG. C6 a depicts the steps in the Alarm Prediction module of the Alarm Manager.

[0056] FIG. C7 depicts the steps in the Alarm Confirmation module of the Alarm Manager

[0057] FIG. C8 depicts the steps in the Alarm Generation and Escalation module of the Alarm Manager.

[0058] FIG. D depicts the interaction of the offline and online components during the ATP

[0059] FIG. E depicts the interaction of the offline and online components during a given DTP within an ATP.

[0060] FIG. F1 depicts the structure of the configuration database.

[0061] FIG. F2 depicts the structure of the offline details database.

[0062] FIG. F3 depicts the structure of the violation and complaints database.

[0063] FIG. F4 depicts the structure of the SLA contact database.

[0064] FIG. F5 depicts the structure of the network traffic database.

[0065] FIG. F6 depicts the structure of the network topology database.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0066] OMS-Offline and Online

[0067] The primary objective of the present invention is the creation of a subsystem for the offline identification and real-time monitoring of a select set of SLAs termed as critical SLAs wherein the network traffic generated by the users of a network is bound by the SLAs. FIG. A depicts the Overload Monitoring System along with Offline and Online components.

[0068] The offline components of the OverLoad Monitoring System (OMS) 10 of the present invention comprise of a Critical SLA Identification Component, HUB Calculation Component, Region Identifier Component and Forecast Model Component.

[0069] The Critical SLA Identification Component 100 of the OMS-offline of the present invention relates to the analysis of network traffic in terms of network load due to the critical SLAs. The objective of this component is to identify a reduced set of SLAs. The Critical SLA Identification Component ensures that only the adequate subset of SLAs are identified for monitoring purposes sand thereby reducing the network monitor-data flow and consequently the load on the network elements.

[0070] The Region Identifier Component 200 of the OMS-offline of the present invention comprises of a regionalization procedure to identify clusters based on the contiguity of the network elements and further grouping of the nodes that exhibit similar average load (mean) characteristics into Similar Load Sub-Clusters (SLSCs). Further, a node of each SLSC is identified as Master Node and the rest of the nodes in the SLSC are identified as Slave Nodes. Based on the observation that the clusters in general and sub-clusters in particular exhibit similarity in load characteristics, the analysis of traffic within sub-clusters are carried out at two different pre-defined intervals thereby reducing the monitor-data flow.

[0071] The Model Selection Component 300 of the OMS-offline of the present invention comprises of the identification of forecasting models at various time intervals to take into account the traffic fluctuations due to network usage. The need for the interval-based forecasting is based on the observed network usage regularity within intervals. This component uses a forecast procedure to predict the load due to the critical SLAs by applying horizontal and vertical model selection techniques on the historical data. Further, the forecast procedure comprises of an Analysis Interval (AI) Identification Procedure that identifies appropriate forecast models (FM) for each of the AIs.

[0072] The HUB Calculation Component 400 of the OMS-offline of the present invention computes the overall network load due to the identified critical SLAs. The monitoring of a select set of SLAs requires the need to forecast the network capacity utilized by these identified SLAs and thereby enabling the prediction of operator violations.

[0073] The Prediction Component 500 analyzes the forecasted load due to the critical SLA's using the vertical FM for a pre-specified set of future points in time, based on the Time Before Overload (TBOL) point.

[0074] The online components of the OMS 15 of the present invention comprise of the Probe Activation Component, Parent Probe Forecast Component and Alarm Manager Component.

[0075] The Probe Activation Component 700 of the OMS-online of the present invention generates parent probes for critical SLAs and activates the pre-installed probes in the Master Node of each SLSC as master probes and the rest of the nodes in each SLSC as Slave Probes.

[0076] The Parent Probe Forecast Component 900 of the OMS-online of the present invention forecasts the load due to the associated Critical SLA at a future time point Time Before OverLoad (TBOL) units away from the time of forecast and communicates the forecasted load to the Alarm Manager Component (AMC). The Parent Probe Forecast Component further identifies the underlying trend of the forecasted load pattern and also communicates the trend behavior to the AMC.

[0077] The Alarm Manager Component 950 of the OMS-online of the present invention consists of an Alarm Prediction Component, an Alarm Confirmation Component, and an Alarm Generation and Escalation Component, to determine and generate OV alarms at a future time point and further, escalate the alarms in case an acknowledgement for the alarms is not received. The objective of the alarm generation is to help the provider in taking corrective steps a priori to resolve potential network bottlenecks.

[0078] The OMS-Offline Component is invoked periodically and there are two distinct periods, Analysis Time Period (ATP) 20 and Detailed Time Period (DTP) 25. The functions of Critical SLA Identification and Region Identification are performed periodically at ATP intervals while the functions of HUB computation and Forecast Model identification is performed at DTP intervals.

[0079] The network region traffic analysis is performed at two distinct configurable clocks, namely, the master clock and the Slave clock. The master clock frequency (MCF) 30 is much higher than the Slave clock frequency (SCF) 35 to reduce the monitor-data flow across the network. The Master Nodes of each SLSC communicates the SLSC load data to one or more parent probes periodically at MCF intervals.

[0080] The OMS system makes use of multiple databases to store and retrieve SLA and Network related data. The Configuration Database 40 contains the information related to the various configurable entities related to SLAs, periodicity, clock frequencies, upper and lower bounds. FIG. F1 is a description of the Configuration Database. The Offline Details database 45 contains the information required for online monitoring of critical SLAs and alarm generation including the set of Critical SLAs, HUBs, AIs and Forecast Models. FIG. F2 is a description of this database. The above two databases are updated and maintained by OMS-Offline component. The Violation and Complaints Database 50 contains the information pertaining to past violations and complaints related to SLAs. FIG. F3 is a description of this database. The SLA contract database 55 contains the information related to the SLA contracts. FIG. F4 is a description of this database. The Network Topology database 60 contains the information related to the past network traffic. FIG. F5 is a description of this database. The Network Topology database 65 contains the information related to the network topology. FIG. F6 is a description of this database. The above 6 databases are external to the OMS system and the indicated entities are the entities that are of interest to the present invention.

[0081] OMS—Offline functionality

[0082] FIG. B is a block diagram depicting the interaction among different components and databases involved in the offline functionality of the OMS in accordance with the preferred embodiment of the present invention.

[0083] Critical SLA Identification Component

[0084] FIG. B1 describes, schematically, the offline critical SLA identification component of the OMS. Critical SLAs for monitoring and forecasting purposes are determined by identifying four types of SLAs by using automatic SLA selection technique 100 based on an optimization procedure, automatic SLA selection option 160 based on past violation history of the SLAs, a manual SLA selection option 170 based on operator preferences, and manual selection of new SLAs 180.

[0085] The SLA related data required for the identification and selection of Critical SLAs is based on the information contained in the databases 40-65.

[0086] The Automatic SLA selection component 100 uses an optimization procedure to determine the first set of critical SLAs, namely, O-CSLAs. These are the SLAs that are within their contractual bounds and may demand additional bandwidth during the times of network congestion.

[0087] The SLA selection based on violations and complaints (V-CSLAs) component, 160, identifies the second set of critical SLAs for monitoring based on the past SLA violations and complaints. This component further analyses violation data related to SLAs and ranks the SLAs based on the frequency of violation in the decreasing order. The component, 160, also analyses SLA related complaint data, and SLAs are ranked based on the frequency of complaints pertaining to a particular SLA in the decreasing order. The configurable number of SLAs are selected from the above ranked SLAs. The motivation for identifying these SLAs is to reduce the churn rate of the operator by monitoring closely those subscribers who have been experiencing problems while using the network infrastructure.

[0088] The Manual SLA selection component (M-CSLAs), 170, identifies the third set of critical SLAs based on a manual selection by the operator. The Manual SLA selection component allows the operator to select SLAs based on operator's own criteria from the overall list of available SLAs.

[0089] The New SLA component 180, (N-CSLAs), identifies the fourth set of critical SLAs based on SLAs that are newly introduced into the system. Operator selects some of these new SLAs for monitoring purposes based on the prior knowledge about the subscribers. 170, 180 provide additional flexibility to the operator to selectively monitor certain “important” SLAs.

[0090] The final set of critical SLAs is the union of the SLAs obtained from the automatic SLA selection technique based on the optimization procedure (O-CSLAs), past violation history of SLA (V-CSLAs) the manual selection based on operator preference (M-CSLAs) and new SLAs (N-CSLAs).

[0091] The procedure for the identification of O-CSLAs is based on the analysis of the past network traffic over ATP where ATP is a configurable analysis time period. ATP is divided into smaller ATWs and in each ATW the network traffic related to an SLA is analyzed. In order to arrive at a computationally efficient load analysis procedure, the analysis is restricted to select ATWs termed as Sensitive Analysis Time Windows (SATWs).

[0092] FIG. B2 is a flowchart depicting the SLA Load Analysis Procedure and determination of SATWs.

[0093] In step 105, the value of ATP is determined.

[0094] In step 110, ATP is partitioned into contiguous ATWs. Then, in Steps 115 and 120, the load due to an SLA is computed over ATW by observing the time-stamp in the packets related to the SLA.

[0095] In step 130, a Load Ranking Procedure determines the combined aggregate load due to all the SLAs across each ATW and further ranks the ATWs in the decreasing order of the combined aggregated load.

[0096] In step 135, a configurable number of ATWs from the above rank-ordered set, termed as SATWs, are selected. SATWs are ATWs wherein the combined load due to the set of SLAs is relatively high and hence these are the time windows of interest.

[0097] FIG. B3 is a graphical representation of the identification of the SATWs. The figure shows the load due to four SLAs, SLA1-SLA4 and the graph B3-1 shows the aggregated load.

[0098] Based on the combined aggregated loads due to the SLAs, ATWs B3-2 and B3-3 are the candidate SATWs.

[0099] FIG. B4 is a flowchart that describes the O-CSLA Identification Procedure.

[0100] In step 135, an Optimization Procedure is used to determine optimal weights for the set of SLAs at each SATW. The objective of the optimization procedure is to identify a minimum number of SLAs whose minimum variation in the load pattern can cause congestion in the network.

[0101] The optimization routine varies the load due to the set of the SLAs in each SATW based on the constraint that the individual load variations due to SLAs do not exceed the allowable upper bound for that SLA, (Δ_(i)). Δ_(i) is the maximum difference between consecutive peaks in the SATW for the SLA. The second constraint is imposed to ensure that the analysis is when the network is overloaded.

[0102] Let x₁ . . . x_(S) represent the set of SLAs under consideration.

[0103] Let b₁ . . . b_(S) represent the average load due to each SLA over SATW.

[0104] Let L represent the overall network capacity

[0105] The optimization problem with respect to SATW is stated as follows:

[0106] Minimize $\sum\limits_{i = 1}^{s}\quad x_{i}$

[0107] Subject to the following constraints ${\sum\limits_{i = 1}^{s}\quad {b_{i}x_{i}}} > L$

[0108] and

[0109] 0≦(b₁x₁−b₁)≦Δ₁

[0110] 0≦(b₂x₂−b₂)≦Δ₂

[0111] 

[0112] 

[0113] 0≦(b_(S)x_(S)−b_(s))≦Δ_(s)

[0114] As a result of the optimization procedure, the set of SLAs over the identified SATWs are associated with optimal weights (reflected by their x_(i) values).

[0115] In step 135, a Filtering Procedure is applied to the set of SLAs to filter out those SLAs that have crossed their SUBs, in any one of the SATWs.

[0116] In step 150, the aggregated weight for each SLA across the SATWs is determined. The SLAs are further ranked in the increasing order of aggregated weights.

[0117] In step 155 a configurable number of the above ranked SLAs are selected as O-CSLAs.

[0118] Region Identifier Component

[0119] The region identifier component of the offline monitoring system aims at reducing the monitor-data flow across the network, by clustering the nodes in the network. The regionalization of the nodes is SLA-specific and these SLA-specific nodes are further clustered (sub-clusters) based on their average load. Representative nodes are identified for each of these sub-clusters and are termed as Master Nodes (MNs). These MNs ensure that the monitor-data flow across the network is reduced.

[0120] FIG. B5 is a flowchart representing the Node Regionalization Procedure for an SLA.

[0121] In Step 200, physically contiguous regions for the nodes in the network are identified based on a pre-defined hop metric from identified seed nodes. In step 200-a, the number of physically contiguous clusters (k) to be formed is obtained from the configuration database. Then in step 200-b, k nodes are identified as seed nodes in the k clusters, such that the k seeds are mutually farthest apart from each other. In step 200-c, a node is classified into any one of the k clusters based on the node's distance (hop metric, h) from the seeds of each of the k clusters and further placed into the cluster whose seed is <=2h hops away from the node. In case of a tie between clusters, the node becomes a member of that cluster whose members (including the seed) are at a minimum distance from the node. (based on the node's proximity to the members of the cluster). The above steps are repeated till all the nodes in the network have been classified.

[0122] Step 205 of the Node Regionalization Procedure forms CSLA-specific regions for each critical SLA by extracting only those nodes that carry the SLA-related traffic from the above contiguous regions of nodes. Note that there are multiple regions associated with each of the critical SLAs.

[0123] In Step 210 of the Node Regionalization Procedure, a hierarchical clustering procedure is employed to form Similar Load Sub-Clusters (SLSCs) based on the similarity (correlation) exhibited in the load pattern of the nodes of the SLA, within the SLA-contiguous region.

[0124] In step 210-a, the desired number of granularity levels (g) for hierarchical clustering of SLA specific clusters is obtained from the configuration database.

[0125] In step 210-b, initially, the load vectors for the nodes of the SLA are computed at the highest granularity level (i=1).

[0126] In steps 210-c and 210-d, the nodes related to the SLA are classified into SLSC's based on the correlation between the load vectors by starting an initial cluster with a random node and further each of the nodes is classified into one of the existing clusters in case of high correlation or by starting a new cluster otherwise.

[0127] In step 201-e, steps 210-a-210-d are repeated at increasing granularity levels till SLSC's for the SLA have been formed at the desired granularity level. FIG. B6 depicts the hierarchical clustering process at various levels of i.

[0128] In step 210-f, the Node Regionalization Procedure comprises of a procedure to identify a node in the centroid position of the SLSC as the Master Node (MN) and the other nodes are identified as Slave nodes.

[0129] In step 210-g, the Node Regionalization Procedure comprises of a procedure that combines all the singleton clusters obtained from the hierarchical clustering procedure into a cluster of singletons called as VLSC (Variable Load Sub-Clusters).

[0130] FIG. B6 is a diagrammatic representation of the Hierarchical Clustering Procedure.

[0131] In step 215, the Node Regionalization Procedure identifies a randomly selected node as the MN of the VLSC and the other nodes in the VLSC are identified as Slave nodes of the VLSC.

[0132] Model Selection Component

[0133] Online OMS makes use of a forecasting model to predict OVs. There are multiple forecasting models such as ARIMA models, mean-based models and median based models. Model selection refers to the identification of one of the forecasting models that characterizes the traffic data with minimum forecasting error. Therefore, the accuracy and validity of the data collected plays a very important role in model building. The Forecast Model Component of the OMS-offline of the present invention comprises of the identification of forecasting models at various time intervals to take into account the traffic fluctuations due to network usage. The need for the interval-based forecasting is based on the observed network usage regularity within intervals.

[0134] FIG. B7 is a graphical representation of the load due to the SLA and the Identification of Forecast Models.

[0135] FIG. B8 is a flowchart describing the offline Model Selection Component.

[0136] In step 300, the Offline Forecast Procedure divides the ATP into sets of DTP sub-intervals (Dij's) and the Dij's into k Model Windows (MWs).

[0137] In step 305, the correlation among consecutive MWs over the interval of <ts,te>, across the set of ATP's is determined. Initially, ts=t0 and te=ts+MW.

[0138] Step 310 determines the correlation among the MWs and checks if all MWs in the DTP sub-interval have been exhausted. (te+MW<=DTP). If the correlation among the MWs is high and te+MW<=DTP, then the end time-point (t_(e)) is advanced to the next MW (te=te+MW), and step 305 is repeated, else step 315 is performed.

[0139] In step 315, <ts,te-MW>is identified as an Analysis Interval (AI) and steps 305-310 are repeated until the condition te+MW>DTP has been satisfied.

[0140] Step 320 determines if all DTPs across ATPs have been analyzed. If not, the next DTP sub-interval is analyzed, by advancing j in D_(ij) by 1 and step 305 is repeated, else step 325 is performed.

[0141] In Steps 325-330 and 335-340, the SFM is applied to each of the identified AI's using two distinct techniques namely, Horizontal BFM Selection Technique and Vertical BFM Selection Technique.

[0142] In the Horizontal BFM Selection Technique, the SFM is applied to each of the identified AI's in the last D_(ij). The predicted values for the last D_(ij) for each AI are obtained from each model belonging to the SFM, and these values are compared with the actual values from the last D_(ij). The FM that generates the least model error is selected as BFM_(h) for the AI.

[0143] In the Vertical BFM Selection Technique, the SFM is applied to each AI across the past D_(ij)'s to generate predictions for the last Dij, by considering a sufficient set of points in the AI for prediction purposes. The predictions generated by each of the models in the SFM over the last Dij are compared with actual data from the last Dij, and the FM that generates the least model error for the AI is selected as BFM_(v) for the AI.

[0144] In step 345, steps 325-330 and 335-340 are independently repeated for the remaining D_(ij)'s to determine BFMs (BFM_(v), BFM_(h)) for the AI's.

[0145] The Model Selection Component further comprises of a Least Merge Error (LME) procedure to merge consecutive AIs identified for a DTP sub-interval, when the number of AIs are more than a configurable pre-specified value.

[0146] FIG. B9 is a flowchart describing the steps involved in the Merging of Analysis Intervals and FIG. B10 is a graphical representation of Merging of Analysis Intervals procedure.

[0147] In step 345, the number of AI's (AI_NUM) are compared with AI_MAX. Steps 345-365 are repeated until AI_NUM<=AI_MAX is satisfied.

[0148] In step 350, the identified Analysis Intervals (AI_(i)'s) are combined from left to right to form Combined Intervals (CIi's).

[0149] In step 355, the identified BFM_(v)'s (BFM_(v(i)) and BFM_(v(i+1))) and BFM_(h)'s (BFM_(h(i)) and BFM_(h(i+1))) corresponding to the first two AI intervals (AI_(i), AI_(i+1)) are applied to the first CI.

[0150] In step 360, the BFM for the i^(th) CI is determined by computing the merge error by applying BFM_(v(i)), BFM_(v(i+1)), BFM_(h(i)), and BFM_(h(i+1)) independently across CI and selecting the model that generates the Least Merge Error (LME) as the BFM for the CI.

[0151] In step 365, step 355 is repeated if there are more CI's to be analyzed. When all CI's have been analyzed, step 370 is performed.

[0152] In step 370, the BFM that generated the LME among all the CI's is identified as the new AI and the process is repeated until the condition in step 345 is satisfied.

[0153] HUB Calculation Component

[0154] FIG. B11 is a flowchart that depicts schematically, the sequence of events that take place in the determination of the Hard Upper Bound (HUB) for the set of critical SLAs.

[0155] The HUB for bandwidth is defined as the difference between the overall network capacity (NWC) and the forecasted usage upper bound (UUB) for all the non-critical SLAs, wherein the overall network bandwidth is statically determined based on network topology.

[0156] In step 400, the HUB calculation procedure analyses the network traffic to generate traffic data specific to non-critical SLAs (X-SLAs).

[0157] In step 405, the load due to the X-SLAs is forecasted over the DTP interval. In step 410, the forecasted load due to a given X-SLA is partitioned, by dividing DTP into H sub-intervals.

[0158] In step 415, the peak load (UUBi) during the i^(th) (i=1 . . . H) sub-interval in the DTP is determined for the N-CSLA. In step 420, step 415 is repeated for all sub-intervals for the X-SLA.

[0159] In step 425, steps 415-420 are repeated for all the X-SLAs under consideration. In step 430, the HUB value for the i^(th) sub-interval across the set of X-SLAs is computed.

[0160] In step 435, HUB values across the set of X-SLAs for all sub-intervals during the DTP are computed.

[0161] Prediction Component

[0162] FIG. B 12 is a flowchart describing the steps involved in Offline Prediction. The Offline Prediction Component analyzes the forecasted load due to CSLAs using BFM_(v), for a pre-specified set of future points in time based on the Time Before Overload (TBOL) points.

[0163] In step 500, the TBOL Time Points of Prediction (TTPP) set is defined, by considering 2k+1 time points that are ATW apart, around TBOL .

[0164] In step 505, the Offline Prediction Component uses BFM_(v), corresponding to the AI related to the current MCF, to predict load across MCF at ATW intervals for each CSLA.

[0165] In step 510, the overall network load (OFPL) due to all critical SLAs at the TBOL (q^(th)) time-point in the DTP is calculated as below. ${OFPL}_{q} = {\sum\limits_{p = 1}^{s}\quad L_{pq}^{F}}$

[0166] Here, L^(F) _(pq) is the computed load, due to the p^(th) CSLA across the MCF (containing the qth time point), at the TBOL (q^(th)) time-point, and OFPL_(q) is the load due to all CSLAs at the q^(th) time point.

[0167] In Step 515, the Offline Prediction Component compares the overall network load OFPL_(q) at TBOL, calculated in step 510, with that of HUB_(i), where the TBOL time point belongs to the i^(th) sub-interval. If OFPL_(q) is less than or equal to HUB_(i), then the Offline Prediction Component forms (2k+1) p^(th) SLA tuple of zeros and stores this in the Offline Details Database. (Step 520).

[0168] In step 525, as the computed load exceeds the HUBS, the Offline Prediction Component checks if the load L^(F) _(pq) due to the p^(th) CSLA is within the threshold value contractually agreed upon in the SLA (SUB) and whether the usage pattern of the SLA exhibits an upward trend (using a trending procedure) for all the 2k+1 time-points in the TTPP set.

[0169] In step 530, the Offline Prediction Component forms an offline 2k+1-pth CSLATuple of 1's and 0's and stores the tuple information in the Offline Details Database.

[0170] In step 535, the Offline Prediction Component repeats steps 525-530 for all CSLAs.

[0171] In step 540, steps 505-535 are repeated for consecutive MCFs till the end of DTP is reached.

[0172] In step 545, steps 500-540 are repeated for remaining DTPs across ATP.

[0173] OMS—Online functionality

[0174] FIG. C is a block diagram showing different components involved in the online functionality of OMS in accordance with a preferred embodiment of the present invention.

[0175] The online functionality of the OMS of the present invention performs online near-optimal traffic analysis by generating distinct parent probes for each CSLA and activates Universal Network Probes (UNPs) that are pre-installed in the network nodes.

[0176] The UNP of the online functionality of the OMS of the present invention further plays role of Master Network Probes (MNP) for a subset of CSLAs and plays the roles Slave Network Probes (SNP) for another subset of CSLAs.

[0177] It is further the object of the OMS to perform network region traffic analysis based on two distinct configurable clocks, namely, the Master Clock and the Slave Clock wherein the Master Clock Frequency (MCF) is much higher than the Slave Clock Frequency (SCF) to facilitate reduced monitor-data flow across the network.

[0178] It is yet a further object of the OMS of the present invention to perform online near-optimal traffic analysis using the pre-installed UNPs in the identified Master Node of an SLSC/VLSC for a particular SLA.

[0179] It is still a further object of the OMS of the present invention to perform online near-optimal traffic analysis using the pre-installed UNPs in the identified Slave Nodes of an SLSC/VLSC for a particular SLA.

[0180] It is yet a further object of the OMS of the present invention to provide a procedure wherein the master probe dynamically computes the load on the Slave Nodes in the associated SLSC periodically at MCF interval.

[0181] It is still another object of the OMS of the present invention to provide a procedure wherein the parent probe forecast component predicts the load and underlying trend of the predicted load pattern, due to the associated CSLA at a future TBOL time point Yet another object of the OMS of the present invention is to provide a procedure wherein the Alarm Manager Component predicts, confirms and generates alarms for operator violations based on consistency of alarms and further escalates in case of no acknowledgement for the generated alarms.

[0182] The aforesaid objects and further objects, functionalities and advantages of the present invention will be discussed below, encompassing detailed description of the preferred embodiments of the present invention with the help of drawings and referred numerals in the said drawings.

[0183] Probe Activation Component

[0184] The Probe Activation Component 700 of FIG. C of the OMS detailed in FIG. C1 performs near-optimal traffic analysis by using the pre-installed UNPs across the network.

[0185] In step 710, the Probe Activation Component generates a unique parent probe for each critical SLA to collect and forecast relevant time-stamped load data of the associated critical SLA.

[0186] In step 715, the Probe Activation Component reads the cluster specific information i.e. the SLSC- and VLSC-specific information determined in the offline system from the Offline Analysis DB 45.

[0187] In step 720, the Probe Activation Component based on the SLSC information read in step 715 further identifies, for each SLSC, a network element as the MN that performs the role of master probe and communicates the role type to the corresponding pre-installed UNP in MN.

[0188] The Probe Activation Component further identifies the CSLA, which needs to be monitored by a master probe, and passes that as a parameter to the pre-installed UNP that performs the role of master probe.

[0189] The Probe Activation Component further reads the master clock frequency from the configuration DB and passes the MCF as a parameter to the master probe based on which the master probe communicates the collected and estimated monitor-data for the associated SLSC to the parent probe.

[0190] In step 725, the Probe Activation Component based on the SLSC information read in step 720 further identifies the network elements which perform the role of a slave probe and further communicates the role type to the corresponding pre-installed UNP.

[0191] The Probe Activation Component further identifies CSLA that needs to be monitored by the slave probe, and passes that as a parameter to the pre-installed UNP that performs the role of slave probe.

[0192] The Probe Activation Component further identifies the master probe for the slave probes in an SLSC and communicates the identified master probe as a parameter to the slave probes to enable the communication of collected monitor-data to the master probe.

[0193] The Probe Activation Component further identifies the SCF and passes the SCF as a parameter to the Slave probes based on which a slave probe communicates the collected monitor-data to the associated master probe at periodic intervals.

[0194] In step 727, the Probe Activation Component repeats the said procedure of identifying master and slave probes and further communicating parameters to master and slave probes for the all the SLSCs identified for all CSLAs during offline analysis to aid the master and slave probes in the corresponding network elements to generate network monitor-data.

[0195] In step 730 of the said Probe Activation Component, based on the VLSC information read in step 720, further identifies the MN that performs the role of master probe and further communicates the role type to the corresponding pre-installed UNP in MN.

[0196] The Probe Activation Component further identifies the CSLA that needs to be monitored by the VLSC master probe, and passes that as a parameter to the pre-installed UNP that performs the role of master probe.

[0197] The Probe Activation Component further passes the MCF as a parameter to the master probe based on which the master probe communicates the collected monitor-data to the parent probe.

[0198] In step 735, Probe Activation Component based on the VLSC information read in step 720 further identifies the network elements that perform the role of slave probes and communicates the role type to the corresponding pre-installed UNPs.

[0199] The Probe Activation Component further identifies the CSLA that needs to be monitored by the slave probe, and passes that as a parameter to the pre-installed UNP that performs the role of slave probe.

[0200] The Probe Activation Component further identifies the master probe for the slave probes and communicates the identified master probe as a parameter to the slave probes and the slave probes communicate the collected monitor-data to the master probe

[0201] The Probe Activation Component further passes the MCF as a parameter to the slave probes based on which the slave probes communicate the collected monitor-data to the master probe. In case of slave probes that belong to a VLSC, the master probe does not estimate the load of the slave probes, as the nodes in the VLSC do not exhibit similarity in the load pattern.

[0202] In step 737, the Probe Activation Component repeats the said procedure of identifying master and slave probes and further communicating parameters to master and slave probes for the all the VLSCs identified for all CSLAs during offline analysis to aid the master and slave probes in the corresponding network elements to generate network monitor-data.

[0203] Master Probe Component of SLSC

[0204] The Master Probe Component 750 of FIG. C of the OMS detailed in FIG. C2, computes the load due the nodes in an SLSC based on the monitor-data related to the master node and the associated slave nodes.

[0205] In step 755, the Master Probe Component receives role type from the parent probe as a parameter, using which the UNP performs the role of Master Node for an SLSC and henceforth the UNP is referred as the Master Network Probe (MNP).

[0206] Further, the Master Probe Component receives SLA identifier information from the parent probe, which is used by the identified MNP to collect data, related to the designated CSLA.

[0207] Further, the Master Probe Component receives the MCF parameter from the parent probe, which is used by the identified MNP to communicate data related to the designated CSLA at MCF intervals. The said parameters are received periodically at ATP intervals.

[0208] In step 760, the Master Probe Component monitors all packets passing through its node and collects the time-stamped traffic measurements related to the designated CSLA.

[0209] In step 765, the Master Probe Component further computes the load due to its node based on time-stamped traffic measurements collected at its node at ATW intervals.

[0210] In step 770, the Master Probe Component further receives slave node load data from slave nodes at SCF intervals.

[0211] In step 775, the Master Probe Component, further, in case of no recent update from a slave probe, estimates the load due to the slave node, at ATW intervals, based on the recent time-stamped SLA load data received from the slave probe and the proportional change in the master node load. The said estimation is repeated for all slave probes in the SLSC associated with the master node. The said estimation procedure is based on the fact that the master node and the Slave nodes in an SLSC exhibit a similar load characteristic. Further, in step 780, the Master Probe Component computes the overall load due to its SLSC by aggregating the load computed with respect to the master node and the associated slave nodes. Based on the similarity in the load pattern of the nodes in an SLSC, the overall aggregated load is a good approximation of the actual SLSC load.

[0212] In step 785, Master Probe Component further communicates the aggregated load due to its SLSC to the parent probe at master clock frequency intervals.

[0213] In step 790, the Master Probe Component further backs up the load information gathered about its SLSC to a pre-specified location at regular intervals.

[0214] Master Probe Component of VLSC

[0215] The Master Probe Component 800 of FIG. C of the OMS detailed in FIG. C3 computes the load due the nodes in an VLSC based on the monitor-data related to the master node and the associated slave nodes.

[0216] As VLSC is a cluster based on singletons, all the nodes in a VLSC collect data at MCF intervals and the identified master probe collects and communicates the load due to the VLSC at MCF intervals.

[0217] In step 805, the Master Probe Component receives role type from the parent probe as a parameter, using which the UNP performs the role of master Node for a VLSC and henceforth the UNP is referred as the Master Network Probe (MNP).

[0218] Further, the Master Probe Component receives SLA identifier information from the parent probe, which is used by the identified MNP to collect data, related to the designated CSLA.

[0219] Further, the Master Probe Component receives MCF parameter from the parent probe, which is used by the identified MNP to communicate data related to the designated CSLA at MCF intervals. The said parameters are received periodically at ATP intervals.

[0220] In step 810, the Master Probe Component monitors all packets passing through its node and collects the time-stamped traffic measurements related to the designated CSLA.

[0221] In step 815, the Master Probe Component further computes the load due to its node based on time-stamped traffic measurements collected at its node at ATW intervals.

[0222] In step 820, the Master Probe Component further receives Slave node load data from Slave nodes at MCF intervals.

[0223] Further, in step 825, the Master Probe Component computes the overall load due to its VLSC by aggregating the load computed with respect to the master node and the computed load received from the associated Slave nodes at MCF intervals.

[0224] In step 830, Master Probe Component further communicates the aggregated load due to its VLSC to the parent probe at MCF intervals.

[0225] In step 835, the Master Probe Component further backups the load information gathered about its VLSC to a pre-specified location at regular intervals.

[0226] Slave Probe Component

[0227] The Slave Probe Component 850 of FIG. C of the OMS detailed in FIG. C4 computes the load with respects to its node based on the monitor-data related to its node.

[0228] In step 855, the Slave Probe Component receives role type from the parent probe as a parameter, using which the UNP performs the role of Slave Node for an SLSC/VLSC and henceforth the UNP is referred as the Slave Network Probe (SNP).

[0229] Further, the Slave Probe Component receives SLA identifier information from the parent probe, which is used by the identified SNP to collect data, related to the designated CSLA.

[0230] Further, the Slave Probe Component receives SCF parameter from the parent probe, which is used by the identified SNP to communicate data related to the designated CSLA at SCF intervals. The said parameters are received periodically at ATP intervals.

[0231] In step 865, the Slave Probe Component monitors all packets passing through its node and collects the time-stamped traffic measurements related to the designated CSLA.

[0232] In step 870, the Slave Probe Component further computes the load due to its node based on time-stamped traffic measurements collected at its node at ATW intervals.

[0233] In step 870, the Slave Probe Component further communicates the aggregated load due to its node to the associated MNP at SCF intervals.

[0234] In the case of the Slave Probe Component related to a slave node in a VLSC, the SCF is the same as MCF.

[0235] Parent Probe Forecast Component

[0236] The Parent Probe Forecast Component 900 depicted in FIG. C of the OMS comprises of forecasting the load due to CSLAs at a pre-specified set of future points in time called Time before Overload point (TBOL) by analyzing the time-stamped CSLA load data received from the associated MNPs at MCF intervals.

[0237] FIG. C5 is a description of the parent probe forecast component for the p^(th) SLA.

[0238] In step 905, the said Parent Probe Forecast Component receives the load data due the associated p^(th) CSLA from the associated MNPs.

[0239] In step 910, a check is made to determine if the OVA flag is set for the p^(th) CSLA. If so, the TBOL point is defined as the prediction time point and steps 920-A -920-F are performed. This computation is being performed in order to be able to compute the overall network load due to CSLAs at each MCF interval.

[0240] In step 915, the Parent Probe Forecast Component defines TBOL Time Points of Prediction (TTPP) set . The TTPP set comprises of 2k+1 time points that are ATW apart and is formed around TBOL by taking k time points before and after TBOL. When an alarm is predicted by the Alarm manager, the corresponding TBOL point is set as Alarm Set Point (ASP) and the corresponding TTPP set is transformed to an ATPP set. For a particular critical SLA, there are at most a pre-specified number, NASP, of ATPP sets.

[0241] In step 920, the Parent Probe Forecast Component applies BFM_(h) generated during offline analysis, for prediction at the TBOL point, to predict L_(pq), the load due to the p^(th) CSLA at the q^(th) point in the TTPP set for all q=1, 2, . . . , 2k+1.

[0242] Steps 920-A-920-E describe the above procedure in detail.

[0243] In step 920-A, the prediction starts at the prediction time point P_(t) where P_(t) is set to current time point C_(t) initially. In step 920-B, P_(t) is advanced by one ATW interval. Then, in step 920-C, the AI corresponding to P_(t) is identified, wherein the AI's are determined during the offline analysis. In step 920-D, the BFM_(h) corresponding to the AI, is identified. In step 920-E, the load L_(pq) is predicted using the said BFM_(h). In step 920-F, steps 920-A-920-E are repeated till P_(t) advances to the (2k+1)^(th) TTPP/ATPP time point.

[0244] In step 922, Parent Probe Forecast Component determines the usage pattern trend and further sets T_(pq) as 1 if an upward trend is exhibited by the load due to p^(th) CSLA and 0 otherwise, for all q=1, 2, . . . 2k+1 for the q.

[0245] In step 924, the load (L_(pq)) and trend (T_(pq)) data determined in the previous steps for the pth CSLA at all q, q=1, 2, . . . 2k+1, of TTPP set is communicated to the Alarm Manager.

[0246] In steps 925-945, the analysis of each of the NASP ATPP sets is carried out.

[0247] In step 925, a check is made to determine if the ATPP set is defined. If not, step 945 is performed, else step 930 is performed.

[0248] In step 930, the Parent Probe Forecast Component applies BFM_(h) generated during offline analysis to predict L′_(pq), the load due to the p^(th) CSLA at the q^(th) point in the ATPP set for all q=1, 2, . . . , 2k+1.

[0249] In step 935, Parent Probe Forecast Component determines the usage pattern trend and further sets T′_(pq) as 1 if an upward trend is exhibited by the load due to p^(th) CSLA and 0 otherwise, for all q=1, 2, . . . 2k+1 for the q.

[0250] In step 940, the load (L_(pq)) and trend (T_(pq)) data determined in the previous steps for the p^(th) CSLA at all q, q=1, 2, . . . 2k+1, is communicated to the Alarm Manager.

[0251] Step 945 is repeated NASP times, by incrementally advancing the ATPP set.

[0252] Step 950 repeats steps 910-945 for all CSLA's.

[0253] Alarm Manager Component

[0254] The Alarm Manger Component (AMC) of the OMS depicted in FIG. C6-FIG. C8 comprises of three important modules, namely, Alarm Prediction, Alarm Confirmation and Alarm Generation & Escalation with respect to operator violation alarms. The Alarm prediction component sets an ASP, for a CSLA, if there is a predicted network overload at a given TBOL time point based on horizontal prediction model. The Alarm Confirmation component confirms the ASP and sets Operator Violation Alarm (OVA) Flag, if there is a consistent overload at successive NASP MCF intervals. The Alarm Escalation Component generates the alarm if OVA flag is set and further escalates in case no acknowledgement is received for the generated alarm. The figure FIG. 6C depicts the execution flow among the various modules of AMC

[0255] FIG. C6 a describes Alarm Prediction module of AMC.

[0256] In step 955, the Alarm Prediction module receives the load data L_(pq) due to all CSLAs at all q points of the (TTPP) set, (q=1, 2 . . . 2k+1) at MCF intervals. In step 960, the overall ${OFPL}_{q} = {\sum\limits_{p = 1}^{s}\quad L_{pq}^{N}}$

[0257] load due to all CSLAs at the q^(th) time point, where q corresponds to the TBOL time point is calculated as below.

[0258] In step 965, the Alarm Prediction module compares the overall network load ONPLq calculated in step 960 with HUB_(i) (HUB value for the i^(th) sub-interval) determined in the offline system, where i is the i^(th) sub-interval containing TBOL time point. The HUB for bandwidth is the difference between the overall network capacity (NWC) and the forecasted usage upper bound (UUB) for all the non-critical SLAs.

[0259] If ONPL_(q) is less than or equal to HUB_(i) then Alarm Prediction module stops further analysis, as the network is not overloaded.

[0260] In step 970, Alarm Prediction module checks whether OVA flag is set for p^(th) CSLA. If set the Alarm Prediction module stops further analysis of p^(th) CSLA as the p^(th) CSLA is already in the predicted list and continues with the processing the next CSLA.

[0261] In step 975, as the computed load exceeds the HUB_(i), the Alarm Prediction module checks if the load L_(pq) due to p^(th) CSLA at the q^(th) time point in the TTPP set, is within the threshold value contractually agreed upon in the SLA (SUB) and further checks whether the usage pattern of the CSLA exhibits an upward trend using a trending procedure. The Alarm Prediction module checks the said condition for all q=1, 2 . . . 2k+1.

[0262] In case of failure of one of the above-mentioned conditions for any one q, the Alarm Prediction module stops further analysis of p^(th) CSLA as the p^(th) CSLA may not cause any operation violation and performs step 985.

[0263] In step 977, the Alarm Prediction module forms an online 2k+1−pth CSLATuple of 1's as the operator violation condition is satisfied for all q=1, 2 . . . 2k+1.

[0264] In step 978, the Alarm Prediction module determines 2k+1-AlarmTuple by combining (AND ing) online 2k+1-pth CSLATuple obtained in the previous step with that of offline 2k+1-pth CSLATuple determined during offline analysis. Both offline and online tuple correspond to the same TBOL time point of the p^(th) CSLA.

[0265] In step 979, the Alarm Prediction module checks whether some k+1 values in the 2k+1-AlarmTuple obtained in the previous step are 1's.

[0266] In case the combined 2k+1-AlarmTuple contains more than k+1 0s, the Alarm Prediction module stops further analysis of p^(th) CSLA and performs step 985

[0267] In step 980, as combined 2k+1-AlarmTuple contains k+1 1's, Alarm Prediction module sets the corresponding TBOL as ASP and further transforms the TTPP set to ATPP set for the p^(th) CSLA at that MCF

[0268] In step 985, the Alarm Prediction module repeats steps 970-980 for all the critical SLAs.

[0269] The figure FIG. C7 depicts Alarm Confirmation Module of AMC.

[0270] In step 1000, the Alarm Confirmation module checks whether the ATPP set for the p^(th) CSLA is defined. Further, in step 1005, the module receives the load data L′_(pq) and trend values from parent probe forecast component for the p^(th) CSLA, for all q=1, 2 . . . 2k+1 in ATPP set.

[0271] In Step 1007, the Alarm Confirmation module checks if the load L′_(pq) due to pth CSLA at the qth time point in the ATPP set, is within the threshold value contractually agreed upon in the SLA (SUB) and further checks whether the usage pattern of the CSLA exhibits an upward trend using a trending procedure. The Alarm Confirmation module checks the said condition for all q=1, 2 . . . 2k+1.

[0272] If the above-mentioned two conditions are met for any one q, in step 1010, the Alarm Confirmation module forms an online 2k+1-pth CSLATuple with the value as 1 if operator violation condition is met and 0 otherwise.

[0273] In step 1015, the Alarm Confirmation module determines 2k+1-AlarmTuple by combining (AND ing) online 2k+1-pth CSLATuple obtained in the previous step with that of offline 2k+1-pth CSLATuple determined during offline analysis. Both offline and online tuple correspond to the same TBOL time point of the p^(th) CSLA.

[0274] In step 1020, the Alarm Confirmation module checks whether any entry in the 2k+1-AlarmTuple obtained in the previous step contains 1.

[0275] In case all entries in the combined 2k+1-AlarmTuple are 0, the Alarm Confirmation module undefines the corresponding ATPP set for the p^(th) CSLA and continues with the processing of the remaining CSLAs.

[0276] In step 1025, the Alarm Confirmation module repeats steps 1000-1025 NASP times for all the defined ATPP sets.

[0277] In step 1030, the Alarm Confirmation module checks whether the least recent ATPP set is defined. If the least recent ATPP set is defined then in step 1035, the alarm confirmation module further sets the Operator Violation Alarm (OVA) flag for the pth CSLA and undefines all ATPP set for that CSLA and performs step 1040. In case of the least recent ATPP set is not defined, the alarm confirmation module stops analysis of p^(th) SLA, and performs step 1040.

[0278] In step 1040, the steps 1005-1035 is repeated for all CSLAs.

[0279] The figure FIG. C8 depicts the Alarm Generation & Escalation module.

[0280] In step 1050, the Alarm Generation & Escalation module reads the candidate operator information from the configuration database and generates operator violation alarms to the said candidate operators.

[0281] In step 1055, Alarm Generation & Escalation module generates the first-level alarms to first set of candidate operators, for all the CSLAs for which OVA flag is set.

[0282] In step 1060, the Alarm Generation & Escalation module further checks whether acknowledgement is received from those first set of candidate operators for the first-level alarms.

[0283] In case of receipt of acknowledgement within a pre-specified acknowledgement time (AT), the Alarm Generation & Escalation module further checks network overload condition in step 1065 after a pre-specified Mean Time To Repair (MTTR) time. In case network overload is observed in step 1070, the Alarm Generation & Escalation module generates operator alarm again, for pre-specified number of times read from the configuration database, before the same is logged for further action

[0284] In case of overload is not observed in step 1075, the Alarm Generation & Escalation module resets the OVA flag and further in step 1077, generates an SLA Recovery Notification (SRN) to the first set of candidate operators and continues with the processing of remaining CSLAs.

[0285] In case acknowledgement receipt is not received within pre-specified AT, in step 1080, the Alarm Generation & Escalation module further checks for the availability of the next set of candidate operators. If the next set of candidate operators is available, then in step 1085, Alarm Generation & Escalation module escalates by sending second-level alarms to the next set of candidate operators. If the next set of candidate operators is not available, in step 1090, the Alarm Generation & Escalation module logs the alarm information for further action and continues with the processing of remaining CSLAs.

[0286] Interaction between Offline and Online Offline Activities Typical Duration Tasks Performed C-SLA Identification 1 ATP Identify SATW s Identify O-CSLAs Regionalization 1 ATP Identify SLSCs and VLSCs for CSLAs Model Selection For every DTP_(i) Identify AIs over n Identify for each successive ATPs AI BFM_(h) and BFM_(v) HUB Computation For every DTP_(i) Compute UUBs for N-CSLA set over n Compute HUBs successive ATPs for CSLAs

[0287] Sample Scenarios:

[0288] ATP: n weeks, 1 week spanning the interval, SUN 00:00 hrs-SAT 23:59 hrs

[0289] DTP_(i): sub-period of ATP, where i corresponds to different days of the week. (ATP)

[0290] ATW: time-period divisions within 1 ATP

[0291] The sequence diagrams depicted in FIG. D and FIG. E represent the interaction between the offline and online components at ATP and DTP intervals. FIG. D—Sample Scenario—1 depicts the sequence of activities that take place at the end of the ATP. FIG. E—Sample Scenario—2 depicts the sequence of activities that take place during a given DTP_(i) in the ATP.

[0292] Thus, a system and method for CSLA Identification based on bandwidth and near-optimal traffic analysis for forecasting BW-related CSLA operator violations at a future time point has been disclosed. Although the present invention has been described particularly with reference to the figures, it will be apparent to one of the ordinary skill in the art that the present invention may appear in any number of systems that predict SLA violations by near-optimal monitoring of an SLA parameter. It is further contemplated that many changes and modifications may be made by one of ordinary skill in the art without departing from the spirit and scope of the present invention.

ACRONYM LIST:

[0293]  1. ASP ALARM SET POINT  2. AI ANALYSIS INTERVAL  3. AMC ALARM MONITOR COMPONENT  4. AT ACKNOWLEDGEMENT TIME  5. ATP ANALYSIS TIME PERIOD  6. ATPP ASP TIME POINTS OF PREDICTION  7. ATW ANALYSIS TIME WINDOW  8. BFM BEST FIT MODEL  9. BW BANDWIDTH 10. Cl COMBINED INTERVAL 11. CSLA CRITICAL SLA 12. DTP DAILY TIME PERIOD 13. EL ESCALATION LEVEL 14. FM FORECAST MODEL 15. HUB HARD UPPER BOUND 16. LME LEAST MERGE ERROR 17. MCF MASTER CLOCK FREQUENCY 18. M-CSLA MANUAL CSLA 19. MN MASTER NODE 20. MNP MASTER NODE PROBE 21. MTTR MEAN TIME TO REPAIR 22. MW MODEL WINDOW 23. NASP NUMBER OF ASP'S 24. N-CSLA NEW CSLA 25. NWC NETWORK CAPACITY 26. O-CSLA OPTIMAL CSLA 27. OL OVERLOAD 28. OMS OVERLOAD MONITORING SYSTEM 29. OVA OPERATOR VIOLATION ALARM 30. SATW SENSITIVE ANALYSIS TIME WINDOW 31. SCF SLAVE CLOCK FREQUENCY 32. SFM SUITE OF FORCASTING MODELS 33. SLSC SIMILAR LOAD SUB-CLUSTER 34. SN SLAVE NODE 35. SNP SLAVE NODE PROBE 36. SRN SLA RECOVERY NOTIFICATION 37. SUB SOFT UPPER BOUND 38. SV SLA VIOLATION 39. TBOL TIME BEFORE OVERLOAD 40. TTPP TBOL TIME POINTS OF PREDICTION 41. UNP UNIVERSAL NETWORK PROBE 42. UUB USAGE UPPER BOUND 43. V-CSLA VIOLATION CSLA 44. VLSC VARIABLE LOAD SUB-CLUSTER 45. X-SLA NON-CRITICAL SLA 

What is claimed is:
 1. An integrated Overload Monitoring System (OMS), for Critical Service Level Agreement (CSLA) Identification based on bandwidth (BW) and Near-Optimal Traffic Analysis for Forecasting BW-related CSLA Operator Violations at a future time point, comprising of: a) a subsystem for the identification of critical SLAs from the data obtained from external repositories wherein a critical SLA is an SLA which is of strategic importance to an operator and hence requiring the monitoring of the same; b) a subsystem to regionalize (cluster) the nodes in the network, using a hierarchical clustering based on similar load behavior, wherein the nodes under consideration are the nodes in a provider's network; c) a Forecast Model (FM) selection subsystem to select horizontal and vertical usage pattern models based on the usage pattern exhibited in the historical data; d) a subsystem to determine the overall load due to critical SLAs by determining Usage Upper Bound for all non-critical SLAs at periodic time intervals and further reduce the load due to non-critical SLAs from the overall load on the network; e) a subsystem for offline SLA load prediction to predict the load due to a critical SLA at a future time point based on historical traffic data using vertical FM; f) plurality of universal network probes that execute the role of master and/or slave probes to perform a near-optimal analysis of the network traffic for critical SLAs; g) a subsystem for network traffic analysis by the network probes based on two distinct configurable clocks with different frequencies to minimize the monitor-data flow across the network; h) a subsystem for real-time SLA load prediction to predict the load due to critical SLAs at a future time point based on current traffic data using horizontal FM; and i) a subsystem to predict alarm set points based on horizontal and vertical FMs to generate alarms based on alarm set point consistency, and further to escalate in case of no acknowledgement for the generated alarm.
 2. The system of claim 1, wherein said CSLA subsystem comprises of a procedure to determine critical SLAs for monitoring and forecasting purposes using: a) An automatic SLA selection technique to identify SLAs based on an optimization procedure (O-CSLAs); b) Past violation history of SLAs (V-CSLAs); c) Manual selection based on operator preference (M-CSLAs); and d) New SLAs (N-CSLAs).
 3. The system of claim 2 further comprises of an SLA load analysis procedure to compute the load due to the SLA over a predefined analysis time period (ATP), partitioning ATP into contiguous analysis time windows (ATWs), wherein the load due to the SLA is computed over ATWs.
 4. The system of claim 3, wherein said load analysis procedure computes the load for the SLA at each ATW by aggregating traffic (packets) specific to the SLA at any node based on the source time-stamp of packets and dividing by ATW period.
 5. The system of claim 3 further comprises of a ranking procedure wherein the load due to the SLAs at each ATW is aggregated and ranked in decreasing order of load, and a configurable number of ATWs, termed as sensitive ATWs (SATWs) are identified.
 6. The system of claim 2 further comprises of a three-step CSLA-Optimum set identification procedure to identify O-CSLAs.
 7. The system of claim 6, wherein the step 1 of said three-step procedure comprises of an optimization procedure to associate weightage to each SLA over SATWs wherein the optimization procedure minimizes the variation in the load due to SLAs based on the peak load characteristics of the SLAs.
 8. The system of claim 6, wherein step 2 of said three-step procedure applies a filtering procedure over each of the SATWs on each of the weighted SLAs to filter out SLAs that have crossed their Soft Upper Bound (SUB) in any one SATW, wherein SUBs are pre-agreed BW values as per the SLAs.
 9. The system of claim 6, wherein step 3 of the said three-step procedure determines the set of O-CSLAs by ranking the aggregated weights, that pertain to an SLA across SATWs, in an increasing order, from which a configurable number of O-CSLAs are identified.
 10. The system of claim 2 further comprises of CSLA-Violation set identification procedure to identify a configurable number of V-CSLAs wherein CSLAs are selected based on the historical data associated with SLA violations and SLA-related complaints.
 11. The system of claim 2 further comprises of a CSLA-Manual set identification procedure to identify a configurable number of M-CSLAs wherein CSLAs are selected manually based on operator preferences.
 12. The system of claim 2 further comprises of a CSLA-NewSLA set identification procedure to identify a configurable number of N-CSLAs based on the agreed upon BW as per the SLA of the new subscribers.
 13. The system of claim 2 comprises of means to obtain a final set of CSLAs as the union of the CSLAs obtained from the CSLA-Optimum set procedure, CSLA-Violation set procedure, CSLA-Manual set procedure and CSLA-NewSLA set procedure.
 14. The system of claim 1, wherein said node regionalization subsystem comprises of a procedure to regionalize nodes wherein the nodes under consideration are the nodes in the provider's network.
 15. The system of claim 14 further comprises of a procedure to identify a contiguous region of nodes based on the number of hops from the identified seed nodes in the network.
 16. The system of claim 15 further comprises of a procedure to form SLA-contiguous regions for each SLA by extracting only those nodes that carry SLA related traffic, from the said contiguous regions.
 17. The system of claim 16 further comprises of a procedure to analyze the load due to an SLA over ATP by partitioning the traffic data into ATWs in each of these SLA-contiguous regions.
 18. The system of claim 17 further comprises of a procedure to compute load vectors for the said ATWs in each of the nodes in each of the said SLA-contiguous regions, wherein the node related traffic data is characterized by the load vector.
 19. The system of claim 18 further comprises of a hierarchical clustering procedure, based on the similarity exhibited in the load pattern within an SLA-contiguous region, to form clusters of load vectors at various hierarchical levels.
 20. The system of claim 19, wherein said hierarchical clustering procedure groups a collection of load vectors with similar mean characteristics into Similar Load Sub-Clusters (SLSCs) based on the correlation among the said load vectors, wherein the elements of each SLSC exhibit similar load pattern behavior.
 21. The system of claim 20 further comprises of a procedure to identify a node in the centroid's position of an SLSC as the Master Node (MN) and other nodes in the SLSC as Slave Nodes (SNs).
 22. The system of claim 19 further comprises of a procedure to identify and combine all singleton clusters obtained from the said hierarchical clustering procedure into a Variable Load Sub-Cluster (VLSC).
 23. The system of claim 22 further comprises of a procedure to randomly identify a node as the Master Node for the VLSC and other nodes in the VLSC are identified as Slave nodes.
 24. The system of claim 1, wherein said forecast model (FM) selection subsystem comprises of a procedure to forecast the load due to an SLA based on the historical data.
 25. The system of claim 24 further comprises of a procedure that applies a suite of numerical forecasting models (SFM) over MaxTBOL and identifies the forecast model that generates the least prediction error based on the historical bandwidth utilization data of the SLA, wherein MaxTBOL is the maximum future time point of interest.
 26. The system of claim 24 further comprises of a forecast procedure that forecasts the load due to SLAs at DTP sub-intervals across a set of ATPs, wherein DTP is a sub-period of ATP.
 27. The system of claim 26, wherein said forecast procedure comprises of an Analysis Intervals Identification procedure based on correlation in SLA load behavior to identify Analysis Intervals (AIs) within each DTP over ATPs.
 28. The system of claim 26 further comprises of a procedure to identify FMs for an SLA using two procedures, namely, Horizontal BFM Model Selection procedure and Vertical BFM Model Selection procedure.
 29. The system of claim 28, wherein said Horizontal BFM Model Selection procedure identifies FMs for an SLA using the corresponding actual data of last DTP to generate predictions and further selecting the FM that generates the least model error as the Best Fit Model (BFM_(h)) for the AI.
 30. The system of claim 28, wherein said Vertical BFM Model Selection procedure identifies FMs for an SLA using the corresponding actual data of previous DTPs to generate predictions and further selecting the FM that generates the least model error as the Best Fit Model (BFM_(v)) for the AI.
 31. The system of claim 24 further comprises of a procedure wherein consecutive AIs are merged into continuous interval (CIs) based on least merge error (LME), when the number of As identified for the DTP are more than the pre-specified number of AIs.
 32. The system of claim 31, wherein said procedure comprises of a procedure wherein the merge error is computed by applying the identified BFM_(v)s and BFM_(h)s corresponding to AIs, across consecutive AIs and selecting the model that generates the LME across the consecutive AIs as the BFM for the CI.
 33. The system of claim 1, wherein said UUB subsystem comprises of a procedure that determines the Usage Upper Bound (UUB) for a non-critical SLA (X-CSLA) by computing the load due to the SLA at ATWs over a pre-specified ATP.
 34. The system of claim 33 further comprises of load analysis procedure to compute the load for an X-SLA at each ATW by aggregating traffic (packets) specific to the SLA at any node based on the source time-stamp of packets and dividing by ATW period.
 35. The system of claim 33 further comprises of a procedure that forecasts the most probable load over DTP due to an X-SLA by analyzing its past load over multiple associated DTPs across ATPs, and further divides the X-SLA load over the DTP into H analysis sub-intervals.
 36. The system of claim 33 further comprises of a procedure to determine the peak load (UUB) at the H sub-intervals for all the X-CSLAs.
 37. The system of claim 35, wherein said procedure is computed for each DTP associated with an ATP.
 38. The system of claim 33 further consists of a procedure to determine the bandwidth hard upper bound (HUB) for CSLAs by computing the difference between the overall network capacity (NWC) and the sum of the forecasted UUBs for all the non-critical SLAs, wherein the overall network bandwidth is the network capacity determined based on network topology.
 39. The system of claim 1, wherein said offline prediction subsystem comprises of a procedure that predicts a network overload at a given TBOL time point and further checks if the load due to the SLA is below its SUB and the usage pattern of the SLA shows an upward trend at the pre-defined points around TBOL.
 40. The system of claim 39, further generates an SLA tuple of Os and is wherein a tuple entry of 1 indicates confirmation to Operator SLA violation wherein the SLA Tuple is used by the online component for generating operator violations.
 41. The system of claim 1, wherein said UNP subsystem comprises of a procedure to pre-install the universal network probe (UNP) in all the network nodes to aid in SLA pre-violation predictions.
 42. The system of claim 41 further comprises of a procedure that installs Slave Node Probes (SNP) in Slave Nodes and Master Node Probes (MNP) in Master Nodes wherein the SNP collects traffic data related to its node and the MNP receives traffic data from SNPs in its SLSC, collects traffic data from its node, and forecasts the load due to the nodes in its SLSC.
 43. The system of claim 1, wherein said parent probe subsystem comprises of a procedure that creates unique parent probes for every critical SLA to forecast the load due to the CSLAs.
 44. The system of claim 41 further comprises of a procedure for network traffic analysis based on two distinct configurable clocks, namely, the master clock and the slave clock wherein the Master Clock Frequency (MCF) is much higher than the Slave Clock Frequency (SCF) to aid in reducing the monitor-data flow across the network.
 45. The system of claim 41 further comprises of a procedure wherein the parent probe associated with a CSLA communicates a set of distinct parameters at ATP intervals to UNPs that need to monitor the traffic related to the CSLA
 46. The system of claim 41 further comprises of a procedure wherein the parent probe associated with a CSLA communicates parameters such as probe type (master), MCF interval and the CSLA related information to the MNPs for the CSLA as per claim 45 at ATP intervals.
 47. The system of claim 41 further comprises of a procedure wherein the parent probe associated with an SLA communicates parameters such as probe type (Slave), the associated MN, SCF and the CSLA related information to the SNPs for the SLA as per claim 45 at ATP intervals.
 48. The system of claim 41 further comprises of a procedure wherein an SNP associated with a CSLA filters and computes the load on the SN and communicates the load data to the associated MNP at SCF intervals.
 49. The system of claim 41 further comprises of a procedure wherein the MNP associated with a CSLA filters and computes the load on the MN at MCF intervals.
 50. The system of claim 41 further comprises of a procedure wherein the MNP estimates the load on the nodes in the associated SLSC at MCF based on the received past traffic data from the SNPs at SCF and its own computed load at MCF.
 51. The system of claim 41 further comprises of a procedure wherein the MNP communicates the associated SLSC forecasted load to the parent probe at MCF.
 52. The system of claim 41 further comprises of a procedure wherein parent probe communicates the same master clock frequency to both slave and master nodes of a VLSC.
 53. The system of claim 41 further comprises of a procedure wherein the MNP computes the load on the nodes in the associated VLSC at MCF based on the received past traffic data from the SNPs at MCF and its own computed load at MCF.
 54. The system of claim 43 further comprises of a procedure that uses a Time Before OverLoad (TBOL) point wherein TBOL is the future time point at which load on the network due to critical SLAs is forecasted.
 55. The system of claim 43 further comprises of a procedure wherein the parent probe forecasts the load due to its associated CSLA at each MCF wherein the forecast is for a set of Time Points Of Prediction (TTPP) around TBOL and the forecast is based on the horizontal prediction model (BFM_(h)) generated during offline analysis for the TBOL point.
 56. The system of claim 43 further comprises of a trending procedure wherein a parent probe analyzes the forecasted load associated with its CSLA and identifies the underlying trend (an upward or downward tendency) of the forecasted load pattern.
 57. The system of claim 1, wherein said Alarm Manager Component subsystem comprises of a procedure that receives the forecasted load and the trend information related to CSLAs from parent probes.
 58. The system of claim 57 further comprises of an Alarm Prediction Module wherein the alarm prediction module, based on the information received from the parent probes, computes the load due to all critical SLAs, and determines an overload condition when the forecasted load exceeds HUB.
 59. The system of claim 58, wherein said Alarm Prediction Module further determines network overload at a given TBOL time point and checks if the load due to the SLA is below its SUB and the usage pattern of the SLA shows an upward trend at all the pre-defined points around TBOL.
 60. The system of claim 58, wherein said Alarm Prediction Module further generates an Online CSLA tuple of Is, if the condition in the system of claim 59 is met.
 61. The system of claim 58, wherein said Alarm Prediction Module further forms an Alarm Tuple by combining the said Online CSLA tuple of is with the CSLA tuple generated during offline analysis, wherein both tuples correspond to the same TBOL time point.
 62. The system of claim 58, wherein said Alarm Prediction Module further predicts an Alarm Set Point (ASP) for the CSLA when the numbers of 1s in the Alarm tuple exceeds a pre-specified value.
 63. The system of claim 57 further comprises of an Alarm Confirmation Module that confirms the ASP, when there is a consistent ASP at a pre-specified number of successive MCF intervals, by setting an Operator Violation Alarm (OVA).
 64. The system of claim 57 further comprises of an Alarm Generation & Escalation Module that associates an alarm escalation level to the said pre-specified candidate operators.
 65. The system of claim 64, wherein said Alarm Generation & Escalation Module further checks the health of the network after a pre-specified MTTR (Mean time to Repair) interval, if it receives an acknowledgement for the OVA alarm.
 66. The system of claim 64, wherein said Alarm Generation & Escalation Module further generates SLA Recovery Notifications (SRNs), wherein SRNs are generated if the health of the network after a pre-specified MTTR is in the recovered state.
 67. The system of claim 64, wherein said Alarm Generation & Escalation Module further re-generates the said OVA alarms if the health of the network after a pre-specified MTTR is not in the recovered state.
 68. The system of claim 64 further comprises of an alarm escalation procedure that further escalates the alarm to the next level of the pre-specified candidate operators after a pre-specified Acknowledgement time (AT), if an acknowledgement is not received for the generated OVA alarm within AT.
 69. An apparatus for CSLA identification based on bandwidth and near-optimal traffic analysis for forecasting bandwidth-related CSLA operator violations at a future time point, comprising of: a) an offline computer system to execute offline procedures; and b) an online computer system to execute online procedures and network probes in network element systems that is part of a provider's network.
 70. The system of claim 69, wherein said offline procedures consists of a procedure for critical SLA identification, a procedure for regionalization of network nodes, a procedure for historical data based selection of forecast models, a procedure for computing overall load due to CSLAs and a procedure for offline operator SLA violation prediction at a future time point based on vertical FM.
 71. The system of claim 69, wherein said online procedures consists of a procedure for creation of unique probes for each CSLA, a procedure in a network element system to perform traffic analysis at master clock frequencies, a procedure in a network element system to perform traffic analysis at slave clock frequencies, a procedure for activation of master and slave probes in network element systems, a procedure to forecast CSLA load at a future time point, a procedure to predict real-time operator SLA violations, a procedure to check operator violation prediction consistency, and a procedure to generate and escalate operator violation alarms.
 72. An apparatus, for CSLA identification based on bandwidth and near-optimal traffic analysis for forecasting bandwidth-related CSLA operator violations at a future time point, coupled to a communication system for communicating plurality of information comprising of: a) offline computational results related to CSLA identification and regionalization at ATP intervals to the online computer system that is part of the said apparatus; b) offline computational results related to vertical FM based load forecast and CSLA load computation at DTP intervals to the online computer system that is part of the said apparatus; and c) traffic analysis results at MCF intervals from network element systems that is part of a provider's network to the online computer system that is part of the said apparatus. 